Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(appset): Fix AppSet Webhook for gitlab merge requests (#13766) #14319

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Syst3m1cAn0maly
Copy link
Contributor

@Syst3m1cAn0maly Syst3m1cAn0maly commented Jul 3, 2023

Closes [#13766]
When using gitlab for the PullRequestGenerator, the webhook doesn't refresh the appset.

When I looked into the code, I noticed that the webhook for PullRequestGenerator for gitlab tries to match the project id with the name.
This fix changes the code so it correctly matches the path/name of the project with the path/name set up in the PullRequestGenerator.

Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Toolchain Guide
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • Optional. My organization is added to USERS.md.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.

Please see Contribution FAQs if you have questions about your pull-request.

@Syst3m1cAn0maly Syst3m1cAn0maly changed the title fix(appset): Fix AppSet Webhook for gitlab merge requests fix(appset): Fix AppSet Webhook for gitlab merge requests issue 13766 Jul 3, 2023
@Syst3m1cAn0maly Syst3m1cAn0maly changed the title fix(appset): Fix AppSet Webhook for gitlab merge requests issue 13766 fix(appset): Fix AppSet Webhook for gitlab merge requests (#13766) Jul 3, 2023
@codecov
Copy link

codecov bot commented Jul 3, 2023

Codecov Report

Patch coverage: 100.00% and project coverage change: -0.13% ⚠️

Comparison is base (ef7f32e) 49.88% compared to head (511c5d9) 49.76%.

❗ Current head 511c5d9 differs from pull request most recent head 7580dad. Consider uploading reports for the commit 7580dad to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #14319      +/-   ##
==========================================
- Coverage   49.88%   49.76%   -0.13%     
==========================================
  Files         263      261       -2     
  Lines       45185    44676     -509     
==========================================
- Hits        22541    22232     -309     
+ Misses      20427    20257     -170     
+ Partials     2217     2187      -30     
Files Changed Coverage Δ
applicationset/webhook/webhook.go 67.09% <100.00%> (ø)

... and 57 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Syst3m1cAn0maly Syst3m1cAn0maly force-pushed the bug-gitlab-pullrequest-webhook branch from 51d53ee to 511c5d9 Compare July 3, 2023 13:22
@Syst3m1cAn0maly Syst3m1cAn0maly force-pushed the bug-gitlab-pullrequest-webhook branch from 511c5d9 to 7580dad Compare September 4, 2023 08:49
@heheh13
Copy link

heheh13 commented May 15, 2024

any update on this pr?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants